We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for the commit author(s). If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google.

Sorry about the spam of commits. I'm not sure what I'm doing with git. It's all new to me.

I'm not sure what to do about the CLA issue since @googlebot claims it found a CLA for me, but not for the committing party, but I am the only committing party.

The build is green now (it was just Travis being flaky)
I will find out what to do about the CLA

The CLA issue is probably because at some point you merged master into your branch.
You could try to rebase removing that commit (and optionally squach your other commits into one).

I was able to manually verify the CLA signature. I'll file a bug against the bot owners to support verification for users with hidden email addresses.

@BobChao87 - we have sorted out the CLA problems; can you address the most recent comments then we can get this merged.

That should do it. The replacer was a good idea, I was clearly too focused on the exact example provided. Thanks @IgorMinar for the CLA fixes.

Checks for the invalid date worked outside. They don't seem to work inside the toJsonReplacer because the date isn't passed in as a Date. I'll try to figure something out.

Indeed. I couldn't figure something out. Maybe this problem is not solveable (at least not without having to traverse the whole object which is obviously out of question).

Or maybe you have better luck figuring something out...

I think as long as the issue can't be fixed satisfactorily, we'll put this into the regular 1.5 milestone.

Here is a hack that fixes this problem:

var DatetoJSON = Date.prototype.toJSON;
Date.prototype.toJSON = function() {
  try {
    return DatetoJSON.call(this);
  } catch(e) {
    if (e instanceof RangeError) {
      return null;
    }
    throw e;
  }
};

The question is how best to sniff for Safari and only do it for that browser?

But since this sort of changing built in global objects is not nice, I think we cannot do this in Angular.
It is a perfectly reasonable workaround for your own apps though...

I'll document this as a known issue, with this workaround over the weekend.
But I think we will have to leave this as it is and close this PR and the related issue.